Maintenance information management system and method of providing a maintenance plan

ABSTRACT

In a maintenance management system and a method of providing support, maintenance information concerning generating plants owned by a user is provided to a maker, and the maker analyzes such items of information, and manages the information in a structure maintenance management system. The user accesses the maintenance management system through the Internet, extracts information to be obtained from databases, and implements maintenance activities or drafts a plan. Engineers of the maker register maintenance information through an intranet, and provide engineering support for the maintenance activities promoted by the user.

BACKGROUND OF THE INVENTION

[0001] The present invention relates to a maintenance informationmanagement system for managing information on the maintenance of powergenerating plants or the like, as well as a method of providing amaintenance plan.

[0002] In the conventional management of generating-plant maintenanceinformation, users store inspection reports submitted by engineersdispatched from makers and technical data presented by makers, and makeseffective use of them as preventive maintenance information. Meanwhile,makers also manage inspection reports and technical data, and indirectlyprovide engineering support for maintenance activities planned by users,by using such data. For example, when a user requires a maker'sengineering support at the time of drafting a maintenance plan, theengineering support is provided in the form of responding to an inquiryfrom the user. Listed below are the details of the generally practicedmanagement of maintenance information and engineering support on thepart of the maker for maintenance activities.

[0003] (1) When conducting maintenance activities such as periodicinspection, the user requests the maker to dispatch engineers, andmanages inspection reports submitted by the maker. Ensuing maintenanceactivities are planned on the basis of these reports.

[0004] (2) The maker stores and manages the inspection reports preparedby the engineers, and rearranges information necessary for the ensuingmaintenance activities as technical data and supplies them to the user.

[0005] (3) At the time of drafting a plan on maintenance activities, theuser takes into consideration the inspection reports and technical datasubmitted by the maker, and studies them. In addition, the user makestechnical inquiries at the maker, as required, through telephone,facsimile, or the like, and drafts the plan on maintenance activities.

[0006] (4) Orders for dispatching of engineers necessary for themaintenance activities, arrangement for parts, and the like are placedwith the maker through a business department.

[0007] (5) Before conducting the maintenance activities, the user andthe maker make arrangements to mutually confirm the details of themaintenance activities, the period of dispatch of trainers, the date ofdelivery of the parts, and the like.

[0008] (6) The user carries out the maintenance activities on the basisof the drafted maintenance plan.

[0009] Namely, when carrying out maintenance activities for a generatingplant, the user drafts a plan on the basis of the inspection reports andtechnical data submitted by the maker, and inquiries about unclearpoints and technical inquiries are made by using telephone andfacsimile. Personnel from the maker visits the user, or personnel fromthe user visits the maker, so as to conduct mutual examination andconfirmation, and the maintenance activities are then carried out.

[0010] It should be noted that, as a system for maintenance managementof documents, including facility drawings, maintenance documents, andthe like of such as plant facilities, Japanese Patent ApplicationLaid-Open Hei 11-85262 (JP-A-11-85262), for instance, discloses atechnique in which document information is managed in a centralizedmanner on the maker side, and information concerning a document issupplied to the user, as required.

[0011] As described above, since the conventional maintenance activitiesare planned on the basis of the maintenance information on a documentbasis, to formulate a maintenance plan by collecting past informationand grasping the trend, a large amount of time and labor are involved inpicking out data, so that much labor has been required on the part ofthe user. Hence, there has been a demand for a technique for performingsuch operations efficiently. In addition, since engineering support forthe user has been conventionally carried out though telephone,facsimile, the mailing of documents, and the like, speedy and accurateengineering support has been desired.

[0012] In addition, although it is described in JP-A-11-85262 referredto above that document information is managed in a centralized manner onthe maker side, the publication is not aimed at providing to the userinformation on the estimation of aged deterioration in the future and amaintenance plan concerning facilities subject to maintenance on thebasis of the maintenance information collected in the past.

SUMMARY OF THE INVENTION

[0013] Accordingly, it is an object of the present invention to providea maintenance information management system and a method of providing amaintenance plan which are capable of appropriately providing amaintenance plan for major component parts of facilities subject tomaintenance.

[0014] To attain the above object, in accordance with the invention,there is provided a maintenance information management systemcomprising:

[0015] a parts management database for storing parts information onmajor parts making up a facility subject to maintenance owned by a user;

[0016] a history management database for storing a history of inspectionor replacement of the major parts concerning said parts managementdatabase; and

[0017] a planning management database for storing a maintenance planconcerning the major parts, the maintenance plan being made on the basisof estimation of a situation of aged deterioration in the futureconcerning the major parts on the basis of data stored in said partsmanagement database and said history management database.

[0018] In addition, in accordance with the invention, there is provideda method of providing a maintenance plan concerning major parts makingup a facility subject to maintenance owned by a user, comprising thesteps of:

[0019] storing in a parts management database parts informationconcerning the major parts making up the facility subject to maintenanceowned by the user;

[0020] storing in a history management database a history of inspectionor replacement of the major parts concerning said parts managementdatabase; and

[0021] estimating a situation of aged deterioration in the futureconcerning the major parts on the basis of data stored in said partsmanagement database and said history management database, and providinga future maintenance plan concerning the major parts to the user on thebasis of the estimation of the aged deterioration.

[0022] In accordance with the invention, an advantage is offered in thatit is possible to provide a maintenance information management systemand a method of providing a maintenance plan which are capable ofappropriately providing a maintenance plan for major component parts offacilities subject to maintenance.

[0023] The above and other objects, features and advantages of thepresent invention will become more apparent from the following detaileddescription of the invention when read in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024]FIG. 1 is a diagram illustrating a generating plant maintenancemanagement system in accordance with an embodiment of the invention;

[0025]FIG. 2 is a diagram illustrating the flow of information in a casewhere this embodiment is used;

[0026]FIG. 3 is a diagram illustrating a specific method ofimplementation of the generating plant maintenance management systemwhich is implemented by a maker;

[0027]FIG. 4 is a diagram illustrating the flow of obtaining andinputting information in the generating plant maintenance managementsystem;

[0028]FIG. 5 is a diagram illustrating the link of information withinthe generating plant maintenance management system;

[0029]FIG. 6 is a diagram illustrating the flow of operation foraccessing each database from a Web server;

[0030]FIG. 7 is a diagram illustrating a screen which is operated by auser and the maker;

[0031]FIG. 8 is a diagram illustrating a screen which is operated by theuser and the maker;

[0032]FIG. 9 is a diagram illustrating the flow of operation of a partsmanagement database;

[0033]FIG. 10 is a diagram illustrating a screen which is operated bythe user and the maker;

[0034]FIG. 11 is a diagram illustrating a screen which is operated bythe user and the maker;

[0035]FIG. 12 is a diagram illustrating a screen which is operated bythe user and the maker;

[0036]FIG. 13 is a diagram illustrating a screen which is operated bythe user and the maker;

[0037]FIG. 14 is a diagram illustrating a screen which is operated bythe user and the maker;

[0038]FIG. 15 is a diagram illustrating the flow of operation of arecords management database;

[0039]FIG. 16 is a diagram illustrating a screen which is operated bythe user and the maker;

[0040]FIG. 17 is a diagram illustrating a screen which is operated bythe user and the maker;

[0041]FIG. 18 is a diagram illustrating a screen which is operated bythe user and the maker;

[0042]FIG. 19 is a diagram illustrating a screen which is operated bythe user and the maker;

[0043]FIG. 20 is a diagram illustrating a screen which is operated bythe user and the maker;

[0044]FIG. 21 is a diagram illustrating the flow of operation of ahistory management database;

[0045]FIG. 22 is a diagram illustrating a screen which is operated bythe user and the maker;

[0046]FIG. 23 is a diagram illustrating a screen which is operated bythe user and the maker;

[0047]FIG. 24 is a diagram illustrating a screen which is operated bythe user and the maker;

[0048]FIG. 25 is a diagram illustrating a screen which is operated bythe user and the maker;

[0049]FIG. 26 is a diagram illustrating a screen which is operated bythe user and the maker;

[0050]FIG. 27 is a diagram illustrating a screen which is operated bythe user and the maker;

[0051]FIG. 28 is a diagram illustrating a screen which is operated bythe user and the maker;

[0052]FIG. 29 is a diagram illustrating the flow of operation of aplanning management database;

[0053]FIG. 30 is a diagram illustrating the flow of operation of theplanning management database;

[0054]FIG. 31 is a diagram illustrating a screen which is operated bythe user and the maker;

[0055]FIG. 32 is a diagram illustrating a screen which is operated bythe user and the maker; and

[0056]FIG. 33 is a diagram illustrating a screen which is operated bythe user and the maker.

DESCRIPTION OF THE EMBODIMENT

[0057] Hereafter, a description will be given of an embodiment of theinvention. It should be noted that although in the following descriptionmaintenance information concerning power generating plants is used as atypical example, the invention can be similarly implemented for plantequipment other than the power generating plants.

[0058]FIG. 1 illustrates a schematic configuration of a generating plantmaintenance management system using a communication network inaccordance with an embodiment of the invention.

[0059] In this embodiment, in power stations A, B, and C on the user 1side where power generating plants are installed, for example, acomputer 2 a is installed as a terminal apparatus used by maintenancepersonnel in the power station A, a computer 2 b is installed as aterminal apparatus used by maintenance personnel in the power station B,and a computer 2 c is similarly installed in the power station C. Thesecomputers 2 a to 2 c are in a state in which communication with theoutside is possible by using a communication line, e.g., in anenvironment in which the Internet 3 can be used. Through the Internet 3the user 1 accesses a Web server 5 for users set up by a serviceprovider. A generating plant maintenance management system 6 which willbe described later is built in this Web server 5, and a fire wall 4 forallowing access to the generating plant maintenance management system 6from predetermined users and preventing unauthorized access from othersis also installed in the Web server 5.

[0060] The generating plant maintenance management system 6 isconfigured by a processing program 7 for displaying a log-in screen anda menu screen and the like for starting the generating plant maintenancemanagement system 6 and for fetching data, as well as a plurality ofdatabases including a parts management database 8 which is a databaseconcerning parts management information on a generating plant open tothe public, a records management database 9, a history managementdatabase 10, and a planning management database 11.

[0061] A service provider 13 (a generating plant maker) provides anengineer in charge of analytical operations in the maker with inspectionreports brought back by engineers dispatched from the maker whenmaintenance activities concerning the user's power generating plantswere carried out, or maintenance information concerning the relevantpower station. On the basis of the maker's knowhow and informationregistered in the generating plant maintenance management system 6, theengineer in charge conducts detailed analysis of the informationincluding the submitted inspection reports and the like. At that time,the engineer in charge at the maker fetches the information registeredin the generating plant maintenance management system 6 through acomputer 15 a for a turbine engineer and a computer 15 b for a generatorengineer, who are clients of an intranet 12.

[0062] The person in charge of turbines or generators registers throughthe intranet 12 the analyzed maintenance information in the variousdatabases including the parts management database 8 to the planningmanagement database 11 of the generating plant maintenance managementsystem 6, and communicates with a system manager that the registrationhas been made. The system manager confirms through a computer 14 for asystem manager that the data have been properly registered, and notifiesthe user through e-male or the like that the registration has beencompleted.

[0063] By using the computers 2 a to 2 c at the power stations throughthe Internet 3, the user reads the maintenance information registered inthe various databases of the generating plant maintenance managementsystem 6 and analyzed by the maker, or downloads the data into thecomputers 2 a to 2 c at the power stations, so as to make effective useof such information on the generating plant in the maintenanceactivities.

[0064] In addition, the user is able to contact the service provider 13and provide necessary information for the future maintenance activitiessuch as information on malfunctions which occurred during the operationof the power generating plants owned by the user. In turn, an engineerin charge in the service provider 13, e.g., a turbine engineer or agenerator engineer, is able to register the provided information in thegenerating plant maintenance management system 6 on the maker side byusing the computer 15 a for the turbine engineer or the computer 15 bfor the generator engineer. Further, on the user side as well, theinformation can be registered in the various databases including theparts management database 8 to the planning management database 11 ofthe generating plant maintenance management system 6 by using any one ofthe computers 2 a to 2 c of the power stations through the Internet 3.

[0065] The maker registers not only the maintenance information providedby the user but also information requiring horizontal development due tomalfunctions or the like occurring in other power generating plants inthe various databases 8 to 11 of the generating plant maintenancemanagement system 6, and notification that such information has beenregistered is given to the system manager. Through the computer 13 forthe system manager the system manager confirms that the data have beenproperly registered, and notifies the user through e-male or the likethat new information has been registered.

[0066]FIG. 2 shows the flow of maintenance information at a time whenthe user engages in maintenance activities by using the generating plantmaintenance management system using the communication network inaccordance with this embodiment, and the maker provides engineeringsupport for the user's maintenance activities. In FIG. 2, by setting asa starting point the implementation 17 of maintenance activities by auser 16, an inspection report 18 is prepared in which the results of theinspection implemented by the user are written, and this inspectionreport is sent to a maker 19 who is a service provider. The makerreceives 20 the inspection report, and an engineer in charge analyzes 21the data in the inspection report. At this time, the engineer in chargeeffects the analysis of the information while making use of pastmaintenance information 23 on the relevant generating plant which isregistered in a maintenance management system 22 and stored in, forexample, the parts management database, the records management database,the history management database, and the planning management database,as well as design information 24, inspection information 25,manufacturing information 26, and similar-model maintenance information27 concerning the relevant generating plant, which are possessed by themaker. The analyzed information is registered 28 a in the maintenancemanagement system 22 by the engineer in charge. Further, the userengineer is also able to register 28 b the data in the databases of themaintenance management system 22. The user 16 accesses the maintenancemanagement system 22 through the communication network, and during theimplementation of the maintenance activities acquires 29 the pastmaintenance information being managed in the maintenance managementsystem 22, or makes effective use of the past information in thedrafting 30 a of a plan for ensuing maintenance activities. The detailsof the planned maintenance activities are presented 30 b to the user.

[0067]FIG. 3 shows specific technical contents at a time when the makeranalyzes the maintenance activities to be provided to the user, andregisters them in this system in accordance with the embodiment. Afteran engineer 32 in charge of each plant enters in the maintenancemanagement system an inspection report 31 in which the results ofmaintenance activities concerning the generating plant carried out bythe user are rearranged, the maker predicts the occurrence ofmalfunctions and the like and extract uninspected portions andweak-point portions by utilizing the past maintenance information on therelevant generating plant already registered and the information onsimilar generating plants possessed by other users. By incorporatinginformation from a maker database 33, in which design information,technical information, and so on concerning each plant possessed by themaker have been registered, into the aforementioned items ofinformation, the maker provides a guideline for optimum maintenanceactivities to the relevant generating plant.

[0068] Next, illustration will be given of an example of support formaintenance activities which is provided by the maker to the user byusing the maintenance management system.

[0069] The data of the inspection reports registered in a recordsmanagement database 34 of this system are automatically transmitted toand stored in a history management database. Then, the trend ofdeterioration of the plant from the past to the present is grasped 37 bya trend management application 36 in the history management database,and a prediction 38 of the trend of future change calculated from itsrate of change is made so as to automatically calculate inspection at anoptimum timing or the period of replacing component parts. Informationon that prediction is presented to the user.

[0070] In addition, information on various phenomena of malfuctionswhich occurred in the past are registered in the history managementdatabase 35. By using a code search function 41, the engineer in chargeof the maker is able to search similar past cases from a historydatabase 39 concerning the relevant generating plant or similar casesfrom a history database 40 concerning similar generating plants. As aresult, it is possible to confirm in a short time the phenomena ofmalfunctions equivalent to the malfunctions which occurred, their causesand countermeasures, and by grasping the frequency 42 of the occurrenceof equivalent malfunctions and incorporating the maker's technicalviews, it is possible to accurately supply necessary information withrespect to the detected malfunction to a user 48. Consequently, the useris able to minimize the period of shutdown.

[0071] Further, by using the history management database 35, it ispossible to easily search uninspected portions 43 and weak-pointportions 44 of the respective plants, and by using a technicalinformation management database 45, it is possible to easily extract aproposal 46 on a new technology which has already been presented to theuser, horizontal development information 47 on malfunctions whichoccurred in other generating plants, and so on. Hence, bit is possibleto accurately supply information required when the user 48 drafts amaintenance plan. As compared with the conventional method in which theuser collects various maintenance information and drafts a maintenanceplan, it is possible to reduce the time required for planning, andcareful drafting 49 of a maintenance plan becomes possible.

[0072] As described above, as the maker provides various maintenanceinformation to the user, the user is able to improve 50 the availabilityfactor of the plants, ensure 51 high reliability, and reduce 52 the lifecost of the generating plants.

[0073]FIG. 4 shows specific processing procedures in a case where theuser obtains or inputs maintenance information by using the generatingplant maintenance management system 6. Namely, FIG. 4 describes thedetails of the processing program 7 shown in FIG. 1.

[0074] The user starts an Internet browser (Step 001), accesses adesignated Web server (Step 002), and logs in to the generating plantmaintenance management system (Step 003). Next, a processing menu isselected (Step 004), and in a case where maintenance information is tobe obtained, an information acquisition screen is opened (Step 005), anda database file in which information to be obtained concerning such asparts, records, history, and maintenance plans is stored is opened (Step006). From the opened database file, the information is read, printedout, or downloaded into the user's personal computer, as required (Step007).

[0075] When maintenance information is inputted by the user, the useropens an information input screen (Step 008) at the time of selectingthe processing menu (Step 004), selects the name of equipment subject toinput (Step 009), and opens a registered database file in whichinformation to be inputted concerning such as parts, records, history,or maintenance plans is stored (Step 010). The user inputs informationin the opened registration database file (Step 011). The inputted datais registered in the database (Step 012). Thus the data inputted by theuser is registered through the internet in the generating plantmaintenance management system managed by the maker.

[0076] In addition, in a case where the user registers maintenanceinformation, the maintenance information is registered in steps similarto the aforementioned steps for the registration of the maintenanceinformation by the user.

[0077]FIG. 5 shows the configuration of the generating plant maintenancemanagement system which is applied to this embodiment, as well as theflow and link of information. The generating plant maintenancemanagement system is comprised of four databases including a partsmanagement database 53, a records management database 54, a historymanagement database 55, and a planning management database 56, which arelinked to each other, whereby the information is provided to a relateddatabase. For example, parts used in the maintenance activities aremanaged by a stock management function provided in the parts managementdatabase, replacement parts information 57 is transmitted to the historymanagement database 55, and required-parts information 58 is transmittedto the planning management database 56. In addition, as the results ofinspection are entered and registered as a record in the recordsmanagement database 54, inspection results information 59 isautomatically registered in the history management database 55. Further,information which is determined to require inspection or partsreplacement is registered in a maintenance work list of the planningmanagement database 56 as required-work information 60 by trendmanagement functions of the records management database 54 and thehistory management database 55. As the maintenance information is thuslinked to each other, information can be effectively utilized.

[0078] Hereafter, referring to diagrams on the system flow and displayscreens of the generating plant maintenance management system in FIGS. 6to 33, a description will be given of various functions, the method ofuse by the user, and the method of providing engineering support to theuser by the maker.

[0079]FIG. 6 shows the flow from the time the user or the maker in anexample of practical application accesses the Web server and logs inuntil the user or the maker accesses each database. As also shown inFIG. 4, the user starts the Internet browser and accesses the Webserver. To open the server, the user logs in 61, and inputs a password62 possessed by an individual user. On the other hand, the maker logs in61 to the system through an intranet. As a result, the system isstarted, and a start screen 63 is displayed, and if the name of thepower station and a unit number are inputted, it is possible to proceedto a database selection screen 64. On this database selection screen,one of the four database names including parts management 65, recordsmanagement 66, history management 67, and planning management 68 isselected, and it is then possible to proceed to the database.

[0080]FIG. 7 shows an example of practical application of the startscreen 63 of the system. In the window in the lower portion of thescreen, a power station name 69 and a unit number 70, which are selectedfrom pulldown menus of the power station name and the unit number, areentered.

[0081]FIG. 8 shows an example of practical application of the databaseselection screen 64. The four database names of the parts management 65,the records management 66, the history management 67, and the planningmanagement 68 are shown in the left window of this screen, and an itemto be accessed is selected from among them. If the database name isselected, equipment names 71 under large classification located in itslower layer are displayed in a pulldown menu, and if one equipment nameis selected, it is possible to proceed to each database.

[0082] Next, a description will be given of the flow and the respectivescreen configuration after the access to each database. First, the flowof the database of the parts management 65 is shown in FIG. 9.

[0083] In FIG. 9, if one of the equipment under large classification inthe parts management database is selected, an equipment selection screen1 (72) is displayed. Here, the arrangement provided is such thatequipment under medium classification can be selected from a systemdiagram. Next, if one of the equipment under medium classification isselected, an equipment selection screen 2 (73) is displayed to allowequipemnt under small classification to be selected. In the partsmanagement, an assembly drawing/parts list 74 of equipment under smallclassification and its detailed parts list 75 can be viewed, andnecessary information can be extracted or downloaded into the individualpersonal computer. Further, the quantities of parts in stock shown inthe detailed parts list 75 show the latest information of the datamanaged by a spare parts management list 76.

[0084]FIG. 10 shows an example of practical application of the equipmentselection screen 1 (72). If one of equipment name buttons 77 undermedium classification to be viewed is clicked in the system diagram onthe screen, it is possible to proceed to a selection screen forselecting equipment under small classification concerning thatequipment.

[0085]FIG. 11 shows an example of practical application of the equipmentselection screen 2 (73). If one of name numbers 78 of equipment undersmall classification to be viewed is clicked in the list on the screen,it is possible to access parts management information concerning thatequipment.

[0086] In the parts management information, an assembly drawing or across-sectional view of the equipment is displayed in FIG. 12, wherebyit is possible to confirm the configuration of the parts of theequipment and parts names. If it is desirous to obtain detailedinformation on the respective parts, one of parts numbers 79 in theassembly drawing or the cross-sectional view or one of parts numbers 80in the parts list is clicked.

[0087]FIG. 13 shows an example practical application of detailedinformation 81 on parts. The part selected on the previous screen isdisplayed by being differentiated in color 82 from other parts. As for astock column 83 on this screen, the latest information is displayed by aparts stock management database which will be described later, so thatthe user or the maker is able to confirm the stock of parts of theequipment for which maintenance activities are to be implemented in thefuture, and the user is able to confirm the need for placing an orderfor necessary parts with the maker. In addition, the maker is able torecommend parts necessary for the future maintenance activities. (Stockmanagement is conventionally carried out on the user side, and therehave been cases where a shortage of parts is confirmed immediatelybefore or during the implementation of the maintenance activities,possibly causing a delay or prolongation of the maintenance activities.)

[0088]FIG. 14 shows an example of practical application of the partsstock management database. A parts warehousing/delivery management list84 is implemented by this database and makes it possible to confirm theparts which have been ordered and used by year as well as the presentquantities of the stock.

[0089] Next, FIG. 15 shows the flow in the case of accessing the recordsmanagement database. If the records management 66 is accessed afterselecting equipment under large classification in the flow describedwith reference to FIG. 6, an equipment selection screen 3 (85) similarto FIG. 8 concerning the parts management is displayed to allow the nameof equipment under medium classification to be selected. If theequipment name is selected, the screen proceeds to a record sheetselection screen 86 displaying the names of record sheets concerning therelevant equipment, and a record to be inputted in or viewed can beselected from this screen.

[0090] Record sheets are largely classified into check sheets 87 andrecord sheets 88. The check sheets 87 are provided to grasp the contentsof the overall activities carried out for the relevant equipment duringthe maintenance activities. During inputting, the presence or absence ofthe implementation of detailed items of work, their results, and whetherthe results were satisfactory or unsatisfactory are entered. When thedata are entered for the respective detailed items of work, a historyinput sheet is automatically displayed. Detailed information on themaintenance activities, photographs taken or sketches drawn during themaintenance activities, and the like can be stored in this sheet. Thisdata is automatically sent to the history management database as historymanagement information which will be described later, and as for theitems to be reflected on the future maintenance activities, it ispossible to allow information to flow to a maintenance plan. Inaddition, when making an entry in the check sheet or viewing it, in acase where the criteria is to be confirmed, it is possible to proceed tocriteria 90 by clicking a criteria button. Further, in a case where theresults of the past maintenance activities are to be viewed, data to beviewed can be selected from a pulldown menu displaying the year/month ofimplementation of activities on the screen, thereby allowing past data91 to be viewed freely. However, the past data 91 is softwarewise lockedto prevent input to or correction of the past data.

[0091] In addition, the record sheet 88 is used for inputting andstoring inspected and measured data in the maintenance activities. Thedata inputted in this record sheet 88 is linked so that it can beutilized as trend management data in history management which will bedescribed later. Further, when past data 92 is to be viewed, viewing ispossible in a procedure similar to that for the check sheet.

[0092]FIG. 16 shows an example of practical application of the recordsheet selection screen 86. If a number 93 on the screen is clicked, itis possible to proceed to a record sheet to be inputted in or viewed.

[0093]FIG. 17 shows an example of practical application of the checksheet 87 for equipment maintenance activities. Here, a list of items 94of maintenance activities to be implemented in the maintenanceactivities is shown, and the presence or absence 95 of implementation ofthe detailed items of work, their results 96, and whether the resultswere satisfactory or unsatisfactory 97 are entered. As a result, it ispossible to enter or view the results of maintenance activitiesconcerning the respective equipment. When the results of the maintenanceactivities are entered, the results can be automatically registered inthe history management database which will be described later.

[0094]FIG. 18 shows a history input sheet for registering maintenancedata in the history management database. This sheet is provided for eachdetailed item of work of the aforementioned check sheet, and when theinput of data in the check sheet is completed, the sheet isautomatically displayed. During the input in the history input sheet,input is automatically made in a unit number 98 and the name 99 ofequipment under medium classification which have already been set. Inaddition, input is also automatically made in a year/month 100 ofimplementation of inspection, the equipment name 101 under smallclassification, parts name 102, work/inspection name 103. If the resultsof inspection are satisfactory, no input is made in phenomena 104, cause105, and countermeasure 106, and a display is given in a comments column107 that there is no abnormality. If an inputter desires to add commentsor input a bit-map file 108 such as a photograph or a related record109, registration is made by inputting its file name. If the resultswere unsatisfactory, the data inputter is able to input in the phenomena104, the cause 105, and the countermeasure 106 by selecting from theirpulldown menus, and also inputs in the comments column 107, the bit-mapfile 108 such as a photograph, and the related record 109. These itemsof information are registered as the history data. In addition, if theresults are those of items to be implemented on a continuous basis inthe future maintenance activities, the data can be also registered inthe maintenance plan by clicking a reflection button 110.

[0095] In addition, during the entry in or viewing of the check sheet 87for equipment maintenance activities shown in FIG. 17, when it isdesirous to confirm the criteria 90 of design values, management values,and the like with respect to these results of the maintenanceactivities, if an access button 111 for accessing a management valuelist at upper right in the screen in FIG. 17 is clicked, it is possibleto access a management value list 112 shown in FIG. 19.

[0096] Further, in FIG. 17, when it is desirous to view the results ofthe past maintenance activities, it is possible to do so by selectingthe year/month of implementation from a registered data column 113 atupper right on the screen.

[0097] When entering the results of individual maintenance activities ina predetermined record sheet or viewing them, the name of the recordsheet for inputting or viewing is selected in FIG. 16. FIG. 20 is oneexample of the record sheet. The results of inspection are entered in arecord input sheet 114. Here again, in a case where the results of pastmaintenance activities are to be viewed, viewing is possible byselecting the year/month of implementation of activities in a registereddata column 115 at upper right on the screen.

[0098] The data registered in FIG. 20 are stored as a record ofmaintenance activities in the database, and are also utilized asinformation on trend management in the history management database. Adetailed description will be given of this information in the item ontrend management.

[0099] Next, the flow in the case of accessing the history managementdatabase is shown in FIG. 21. If the history management 67 is accessedafter selecting equipment under large classification in the flowdescribed with reference to FIG. 6, an equipment selection screen 4(117) is displayed to allow the name of equipment under mediumclassification to be selected.

[0100] When the system diagram of the selected equipment is displayed,and the name of the equipment is selected, the operation proceeds to thehistory item selection screen 117 concerning the relevant equipment.From this screen, a history item to be viewed is selected. Here, theequipment is not classified into small groups of classification in themanner of the parts management and the records management, and theoperation proceeds to a screen to be viewed by using the historymanagement menu. The reason for this is that there are items ofmaintenance information which are related to each other among the mediumgroups of classification.

[0101] The history items include history list selection 118, technicaldata 119, and data trend selection 120, a search code corresponding toeach equipment is related to the history list selection 118, and searchis possible by designating a code, so that it is possible to proceed toa detailed chart 121 of the registered data. In the technical dataselection 119 as well, a list is displayed, and it is possible toproceed to individual technical data 122 from its number. If the trendselection 120 is selected, a trend graph 123 on the item being managedis displayed, and by clicking a trend prediction button on the graphscreen, a graph of trend prediction 124 is displayed.

[0102]FIG. 22 shows an example of practical application of the historyitem selection screen 117. If a number 125 in the list on the screen isclicked, it is possible to proceed to the history list 118, thetechnical data 119, and the data trend 120.

[0103]FIG. 23 shows an example of practical application of the historylist 118. A column 126 for designating a code for search is provided inan upper portion of the screen, and if an item to be confirmed iscode-searched, the user or the maker is able to view a history list 127.

[0104] For example, in a case where the user or the maker desires toknow what inspection was performed during the previous maintenanceactivities with respect to the designated equipment and what were theresults, viewing is possible if search is made by selecting a unit name128, a facility name 129, and year/month 130 from their pulldown menus.Alternatively, if it is desirous to know the frequency of occurrence ofa certain phenomenon, chronologically arranged information can be viewedif search is made by selecting the facility name 129 and a phenomenoncode 131 from their pulldown menus.

[0105] Further, when it is desirous to view the detailed chart 122registered in the history list 127, if an item to be confirmed in thehistory list 127 is clicked, it is possible to proceed to the detailedchart screen shown in FIG. 24, and view detailed data, photographs, andthe like.

[0106] Consequently, when drafting a maintenance plan, the user is ableto reflect an item to be implemented on future maintenance activities onthe basis of the actual results of the past. Meanwhile, the maker isable to compare items of information on a plurality of generating plantsbeing managed by this system, so that the maker is able to easilypresent a proposal for more reliable maintenance activities to the user.

[0107]FIG. 25 shows an example of practical application of a list screenwhen it is desirous to access technical data. Here again, it is possibleto select an item to be viewed by using a code search column 132, andthe results of search are displayed in a list 133. Further, if an itemis clicked, the details of the technical data can be viewed.

[0108] Next, a description will be given of access to trend management.FIG. 26 shows an example of practical application of a menu screen ofdata trend. If a number 134 in the menu is clicked, it is possible toproceed to a trend graph.

[0109]FIG. 27 shows one example in which items of trend managementnecessary for the maintenance activities of various equipment are shownin a graph 135. Consequently, it is possible to graph the trend ofchange of the state of use of the equipment and provide information forthe planning of maintenance activities.

[0110] Further, if a prediction curve button 136 at upper right on thescreen of FIG. 27 is clicked, the operation proceeds to a screen forpredicting the future trend of change estimated from the average rate ofchange in the results of inspection conducted three times in the past.FIG. 28 shows an example of practical application of the trendprediction screen. This trend prediction screen has the function ofautomatically calculating and displaying dates which exceed themanagement values set in the graph. Consequently, the user is able toplan maintenance activities more efficiently, and the maker is able toeasily present and recommend technical data corresponding to theinformation.

[0111] Next, the flow in the case of accessing the planning managementdatabase is shown in FIG. 29. If the planning management 68 is accessedafter selecting equipment under large classification in the flowdescribed with reference to FIG. 6, an equipment selection screen 5(137) is displayed to allow the name of equipment under mediumclassification to be selected.

[0112] If the name of the equipment is selected from the system diagramof the selected equipment, the operation proceeds to a planning itemselection screen 138 concerning the relevant equipment, and a planningitem to be viewed is selected. Here again, the operation does notproceed to the classification of equipment into small groups in the sameway as the history management, and the operation proceeds to a screen tobe viewed by using the planning item menu. The reason for this is thatthere are items of maintenance plan information which are related toeach other among the medium groups of classification.

[0113] Planning items include a maintenance plan list 139 in which workplan items registered in the record management and the historymanagement are displayed in the form of a list, a customer input 140 forinputting a work plan drafted voluntarily by the user, and a yearlymaintenance plan 141 in which work items are registered by year. If theyear of implementation is designated in the maintenance plan list 139,and if the year of implementation is designated in the customer input140, automatic registration can be made in the yearly maintenance plan141.

[0114]FIG. 30 shows an example of practical application of the planningitem selection screen. If a number 142 in the menu is clicked, theoperation proceeds to a screen to be viewed or inputted in.

[0115]FIG. 31 shows an example of practical application of themaintenance plan list. A list of maintenance activities to beimplemented in the future is displayed in this list. The user studieswhich work is to be carried out during the period of maintenanceactivities in the future, and clicks a number 143 of the registered workitem. Further, if the user designates a scheduled period ofimplementation in a year/month window 144 in an upper portion of thescreen, and clicks a registration button 145, registration can be madein the yearly maintenance plan list.

[0116]FIG. 32 shows an example of practical application of the customerinput. In a case where there is an item of work which the user desiresto implement apart from a proposal from the maker, the user registersthe work item on this screen. If the user clicks a number 146 of theregistered work item, designates a scheduled period of implementation ina year/month window 147 in an upper portion of the window, and clicks aregistration button 148, registration can be made in the yearlymaintenance plan list.

[0117]FIG. 33 shows an example of a screen which displays a list ofmaintenance activities registered by year. By using this screen, theuser and the maker are able to grasp the contents of maintenanceactivities to be implemented in the future, and the user carries out thedrafting of detailed schedules of maintenance activities and thearrangement for necessary parts. In addition, the maker is able to graspthe operation and parts arranged for by the user and proceed with theplan, and if there is any shortage of work in the maintenance activitiesscheduled by the user, the maker makes a recommendation or a proposal.

[0118] As described above, in this embodiment, maintenance informationconcerning generating plants owned by the user is formed into databaseson the maker side, and the user accesses via the communication networkthe plant management system managed by the maker, thereby making itpossible to speedily obtain orderly rearranged maintenance informationaccurately and easily. Thus it becomes possible for the customer'smaintenance activities to be implemented efficiently. In addition,although the input and management of data are carried out by the makerwho acts as a principal entity, the input is made possible from the userside as well, as necessary. Thus, since both the user and the makershare the maintenance information on the facilities, it becomes possibleto make effective use of the information mutually and implement themaintenance activities of the facilities smoothly and rationally.

[0119] Namely, in this embodiment, since the maker who has muchtechnical information analyzes the results of maintenance activitiescarried out by the user, it becomes possible to grasp the situation ofthe generating plants more accurately. Hence, in accordance with thisembodiment, information on the estimation of aged deterioration in thefuture and maintenance plan information concerning component equipmentof facilities subject to maintenance can be timely provided from themaker side to the user.

[0120] In addition, since the results of analysis conducted by the makerare made available to the user, the user is able to easily confirm thesituation of the generating plates in operation. Additionally, since theuser uses the aforementioned information provided by the maker, the useris able to draft a maintenance plan efficiently, thereby making itpossible to carry out highly reliable maintenance activities.Consequently, it becomes possible to reduce the life cost of thegenerating plants owned by the user.

[0121] In addition, the maker is able to easily grasp from the systemhow the user is operating the generating plants and what maintenanceplans have been drafted, so that the arrangement for parts necessary formaintenance activities, planning for dispatching engineers, and the likecan be conducted efficiently. Accordingly, business merits based on theexchange of maintenance information are produced for both parties, addedvalues in information corresponding to the quality and quantity ofinformation are produced, and information service business isestablished.

[0122] Further, in accordance with this embodiment, since the results ofimplementation of the maintenance activities are stored as databases,with respect to malfuctions and the like which could be confirmed duringthe operation or inspection of the generating plants, the user is ableto readily search, for example, what similar malfunctions occurred inthe past and what countermeasures were taken. Therefore, the user isable to deal with their countermeasure operations in a short period oftime, and reduce the period of shutdown of the operating plants, therebymaking it possible to improve the availability factor.

[0123] In addition, in accordance with this embodiment, from theviewpoint of the user, the management of information on the generatingfacilities owned by the user can be managed by the maker having detailedtechnical information on the generating plants, and the user is able toview reliably maintained data, when necessary. Consequently, it ispossible to implement highly reliable maintenance activitiesefficiently, and improve the job efficiency of user engineers in chargeof the maintenance activities. Meanwhile, the maker is able to sharewith the user the maintenance information concerning the generatingplants owned by the user, and is able to reliably grasp the maintenanceactivities which the user intends to implement, permitting appropriatetechnical support.

What is claimed is:
 1. A maintenance information management systemcomprising: a parts management database for storing parts information onmajor parts making up a facility subject to maintenance owned by a user;a history management database for storing a history of inspection orreplacement of the major parts concerning said parts managementdatabase; and a planning management database for storing a maintenanceplan concerning the major parts, the maintenance plan being made on thebasis of estimation of a situation of aged deterioration in the futureconcerning the major parts on the basis of data stored in said partsmanagement database and said history management database.
 2. Themaintenance information management system according to claim 1, whereinsaid planning management database is arranged such thatwarehousing/delivery information concerning parts information stored insaid parts management database or history information on the inspectionor replacement of the major parts stored in said history managementdatabase can be registered by a service provider for providingmaintenance service concerning the facility subject to maintenance ownedby the user or by the user.
 3. The maintenance information managementsystem according to claim 1, wherein information on similar maintenancework carried out in the past concerning the major parts requiringmaintenance work, on the basis of past maintenance information stored insaid history management database, is stored in said planning managementdatabase.
 4. A maintenance information management system comprising: aparts management database for storing information on parts making up afacility subject to maintenance owned by a user; a history managementdatabase for storing a history of inspection or replacement of the partsconcerning said parts management database; and a planning managementdatabase for storing a maintenance plan concerning the parts, themaintenance plan being made on the basis of estimation of a situation ofaged deterioration in the future concerning the parts on the basis ofdata stored in said parts management database and said historymanagement database.
 5. The maintenance information management systemaccording to claim 4, wherein a list of work items concerning majorparts requiring maintenance activities as a future maintenance plan isstored in said planning management database.
 6. A maintenanceinformation management system comprising: a parts management databasefor storing parts information on major parts making up a facilitysubject to maintenance owned by a user; a records management databasefor storing maintenance records concerning the facility subject tomaintenance; a history management database for storing a history ofinspection or replacement of the major parts on the basis of themaintenance records stored in said records management database; and aplanning management database for storing a maintenance plan concerningthe parts, the maintenance plan being made on the basis of estimation ofa situation of aged deterioration in the future concerning the parts onthe basis of data stored in said parts management database and saidhistory management database.
 7. A method of providing a maintenance planconcerning major parts making up a facility subject to maintenance ownedby a user, comprising the steps of: storing in a parts managementdatabase parts information concerning the major parts making up thefacility subject to maintenance owned by the user; storing in a historymanagement database a history of inspection or replacement of the majorparts concerning said parts management database; and estimating asituation of aged deterioration in the future concerning the major partson the basis of data stored in said parts management database and saidhistory management database, and providing a future maintenance planconcerning the major parts to the user on the basis of the estimation ofthe aged deterioration.
 8. The method of providing a maintenance planaccording to claim 7, wherein warehousing/delivery informationconcerning parts information stored in said parts management database orhistory information on the inspection or replacement of the major partsstored in said history management database is registered by a serviceprovider for providing maintenance service concerning the facilitysubject to maintenance owned by the user or by the user.
 9. The methodof providing a maintenance plan according to claim 7, whereininformation on similar maintenance work carried out in the pastconcerning the major parts requiring maintenance work, on the basis ofpast maintenance information stored in said history management database,is provided to the user.
 10. The method of providing a maintenance planaccording to claim 7, wherein a list of work items concerning the majorparts requiring maintenance activities as a future maintenance plan isprovided.
 11. A method of providing a maintenance plan concerning partsmaking up a facility subject to maintenance owned by a user, comprisingthe steps of: storing in a parts management database parts informationconcerning the parts making up the facility subject to maintenance ownedby the user; storing in a history management database a history ofinspection or replacement of the parts concerning said parts managementdatabase; and estimating a situation of aged deterioration in the futureconcerning the parts on the basis of data stored in said partsmanagement database and said history management database, and providinga future maintenance plan concerning the parts to the user on the basisof the estimation of the aged deterioration.
 12. A method of providing amaintenance plan concerning major parts making up a facility subject tomaintenance owned by a user, comprising the steps of: storing in a partsmanagement database parts information concerning the major parts makingup the facility subject to maintenance owned by the user; storing in arecords management database maintenance records concerning the facilitysubject to maintenance; storing in a history management database ahistory of inspection or replacement of the major parts stored in therecords management database; and estimating a situation of ageddeterioration in the future concerning the major parts on the basis ofdata stored in said parts management database and said historymanagement database, and providing a future maintenance plan concerningthe major parts to the user on the basis of the estimation of the ageddeterioration.
 13. A maintenance information management systemcomprising: a parts management database for storing parts information onmajor parts making up a generating plant facility subject to maintenanceowned by a user; a history management database for storing a history ofinspection or replacement of the major parts concerning said partsmanagement database; and a planning management database for storing amaintenance plan concerning the major parts, the maintenance plan beingmade on the basis of estimation of a situation of aged deterioration inthe future concerning the major parts on the basis of data stored insaid parts management database and said history management database. 14.A method of providing a maintenance plan concerning major parts makingup a generating plant facility subject to maintenance owned by a user,comprising the steps of: storing in a parts management database partsinformation concerning the major parts making up the generating plantfacility subject to maintenance owned by the user; storing in a historymanagement database a history of inspection or replacement of the majorparts concerning said parts management database; and estimating asituation of aged deterioration in the future concerning the major partson the basis of data stored in said parts management database and saidhistory management database, and providing a future maintenance planconcerning the major parts to the user on the basis of the estimation ofthe aged deterioration.